* actions that act on that document (eg. save, cut/copy/paste, etc). Each
* window's menus would be constructed from a combination of two action
* groups.
- * </para>
+ *
* <para id="Action-Accel">
* Accelerators are handled by the GTK+ accelerator map. All actions are
* assigned an accelerator path (which normally has the form
* and toolitems take on this accelerator path. The GTK+ accelerator map
* code makes sure that the correct shortcut is displayed next to the menu
* item.
+ * </para>
*
* <refsect2 id="GtkActionGroup-BUILDER-UI">
* <title>GtkActionGroup as GtkBuildable</title>
* example, when an Open button is clicked you might display a
* #GtkFileChooserDialog. After a callback finishes, GTK+ will return to the
* main loop and await more user input.
- * </para>
+ *
* <example>
* <title>Typical main() function for a GTK+ application</title>
* |[<!-- language="C" -->
* }
* ]|
* </example>
- * <para>
+ *
* It's OK to use the GLib main loop directly instead of gtk_main(), though it
* involves slightly more typing. See #GMainLoop in the GLib documentation.
*/